Timetable-based assignment: Preselection page
On this page, you set the parameters for the selection of found connections.
Note: Some of the parameters on this page are not provided if the option Shortest path search has been checked on the Search page. |
Element |
Description |
Connections with PuT and without PuT on an OD pair |
The settings in the drop-down list apply to OD pairs for which connections with and without public transport have been found. In case of a connection with PuT, at least one line, Aux or Sharing transport system is boarded. In case of a connection without PuT, no PuT transport system is boarded. Only access, egress, and walk links are used. Delete all connections using PuT lines All connections for an OD pair either found by the path search procedure or imported during connection import, that include at least one boarding of a PuT transport system are deleted. Delete all connections without PuT All connections for an OD pair either found by the path search procedure or imported during connection import, that do not include PuT transport system boardings (e.g. using only walk links) are deleted. Note This option is not relevant if, under Calculate > General procedure settings > PuT settings > Assignment > Walk links from/to connectors, you have selected Walk links between zones not permitted or Force boarding/alighting at connected node. In this case, no connections without PuT are found (Restricting the walk link search). Do not delete any connection None of the connections for an OD pair either found by the path search procedure or read in during the connection import is deleted. |
Delete connections that are entirely within the pre-/post-assignment period |
Select this option to delete connections that either arrive within the pre-assignment period, i.e. before the assignment period starts, or depart after the post-assignment period, i.e. after the assignment period ends. Notes Those connections might be found - and loaded - because of the pre-assignment period or post-assignment period in the timetable-based assignment. They may also be read from file. Those connections do not affect most of the skims as they are usually charged with fewer passengers and thus have less weight. However, when calculating the service frequency, each connection is counted. This option can be used to determine the precise number of connections that depart within the assignment period. |
Delete connections that depart before the start of the assignment period |
For departure time related demand segments, select this option to delete connections that depart before the assignment period starts. |
Delete connections that arrive after the end of the assignment period | For arrival time related segments, select this option to delete connections that arrive after the assignment period ends. |
1. Search impedance |
For each OD pair, all connections - either found by the connection search or imported from a connection file - that were not deleted for other reasons yet, are evaluated prior to connection choice. The following criteria are verified. If applicable, connections are deleted. You may adjust the conditions with the help of factors and addends. Note The criteria are checked in exactly that order. 1. Search impedance > factor • minimum search impedance + addend Connections are deleted if their search impedances are very high compared to the minimum search impedance of the OD pair. Notes This option is only provided if either - on the Search page - option Branch & bound search has been checked or after a connection import. The impedance used here corresponds to the Search impedance defined on the Branch and Bound page. |
2. Journey time and number of transfers |
Journey time > factor • minimum journey time + addend and number of transfers > minimum number of transfers or Number of transfers > minimum number of transfers + addend and journey time > minimum journey time To all remaining connections applies: Connections are deleted if two conditions are satisfied: Compared to the minimum journey time per OD pair their journey times are extremely long and their numbers of transfers exceed the minimum number of transfers. Connections are also deleted if these two conditions are satisfied: Their numbers of transfers exceed the minimum number of transfers per OD pair by a certain number of transfers and their journey times exceed the minimum journey time. |
3. Perceived journey time (PJT) |
If the option has been checked, the following applies: Perceived journey time (PJT) > factor • mean PJT + addend To all remaining connections applies: If this option has been checked connections are deleted if their perceived journey time exceeds the mean PJT by OD pair significantly. If multiple demand segments are assigned, then select the Demand segment for the calculation of the perceived journey time from the drop-down list. Notes The selection list is invisible as long as only a single demand segment is to ne assigned. The selection list is grayed out as long as the third condition has not been checked if multiple demand segments are assigned. |